-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libbeat/beat: introduce Beat.OutputConfigReloader #28048
Conversation
Introduce Beat.OutputConfigReloader, an optional reload.Reloadable that may be set by a beat.Creator in order to watch output config changes.
b2e947f
to
e67c93b
Compare
Pinging @elastic/agent (Team:Agent) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Introduce Beat.OutputConfigReloader, an optional reload.Reloadable that may be set by a beat.Creator in order to watch output config changes. (cherry picked from commit 67f2e2b)
Introduce Beat.OutputConfigReloader, an optional reload.Reloadable that may be set by a beat.Creator in order to watch output config changes. (cherry picked from commit 67f2e2b) Co-authored-by: Andrew Wilkins <[email protected]>
Introduce Beat.OutputConfigReloader, an optional reload.Reloadable that may be set by a beat.Creator in order to watch output config changes.
What does this PR do?
Introduce
Beat.OutputConfigReloader
, an optionalreload.Reloadable
that may be set by abeat.Creator
in order to watch output config changes. This will be called in addition to the reloader that libbeat registers internally.Why is it important?
We can hook into the output reloader using this approach to extract the config we require.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Note regarding testing: normally I would write a test for a change like this, but there does not appear to be any framework for writing similar tests. The code is trivial enough that I don't want to get bogged down introducing a framework.